home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr25
/
os2cop21.zip
/
OS2COPY.DOC
< prev
next >
Wrap
Text File
|
1993-04-29
|
25KB
|
328 lines
┌───────────────────────────────────────────────────────────────────────────┐
│ OS2COPY rel. 2.1 by Ståhle (C) │
│ │
│ This packet is designed to Copy an OS/2 v. 2.1 Beta March 1993 │
│ HPFS or FAT BootManager system, fully configured, from one partition │
│ (drive letter) to an other (eg. from D: to F:) │
│ │
│ >> It will NOT work on a plain OS/2 v. 2.0 GA without CSD (= ServicePak) │
│ │
│ This also implies that an entire system including all configuration, │
│ installed on one computer can be copied to another if the hard disk │
│ from the second computer is temporarily installed on the first one. │
│ │
├───────────────────────────────────────────────────────────────────────────┤
│ File list: │
│ │
│ OS2Copy.DOC (this file). │
│ │
│ All of these are required files: │
│ │
│ OS2Copy.CMD Initiates the copy process. │
│ OS2Copy2.CMD Performs the copy process. │
│ InitEdit.Exe Edits the init files. │
│ YesNo.LNG abbreviations for Yes and No in national language │
│ XCopy.Sw switches for XCOPY │
│ InitEdit.LST list of files to be edited │
│ ......................................................................... │
│ │
│ If your OS/2 system is using a national language (ie. other than English) │
│ you +MUST+ edit this file - any 7 bit ASCII text editor will do: │
│ │
│ YesNo.LNG abbreviations for Yes and No in your national language │
│ ......................................................................... │
│ │
│ You may also have to edit this file, any 7 bit ASCII text editor will do: │
│ │
│ InitEdit.LST │
│ (List of files, may need editing especially if you are copying a national │
│ language version other than English). │
│ ......................................................................... │
│ │
│ You may also find it necessary to edit the file (if version > 2.1 beta): │
│ │
│ XCopy.Sw v. 2.1 switches for XCOPY │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ All of the above are Copyright (C): │
│ John Ståhle │
│ 289A Buddinge Hovedgade │
│ DK-2880 Bagsværd │
│ Denmark, Europe │
│ Phone +45 44 98 66 18 (voice) │
│ │
│ You can reach me through the RIME and ILINK international OS/2 │
│ conferences, user name: John Staahle │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ This is what it is all about: │
│ │
│ Two co-operating REXX scripts, and a co-operating program, │
│ designed to Copy an * OS/2 HPFS or FAT BootManager * system from │
│ one drive letter to another, eg. from D: to E: │
│ │
│ There is no obvious reason why this packet should not work on a │
│ 'OS/2 as only operating system' too but this has not yet been tested. │
│ It may even work in a network, this has not been tested either. │
│ │
│ The program interacts with the two OS2Copy.CMDs, (which also interacts) │
│ in performing the actual editing of OS/2 initfiles (OS2.INI and the like)│
│ to fit on a new partition, creating data files for the scripts, etc. │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ How to: │
│ │
│ Prerequisites: │
│ │
│ 1. An installed OS/2 BootManager system │
│ with REXX (part of standard OS/2) installed │
│ │
│ 2. A partition to Copy to :-) │
│ >>> This partition will become formatted during the procedure <<< │
│ >>> AND it will contain ALL files found on the From system. <<< │
│ >>> The latter implies that the From partition must have <<< │
│ >>> room for these files. <<< │
│ │
│ 3. The files listed as Required in the above Filelist. │
│ │
│ >> All these files MUST reside in the subdirectory from which you │
│ >> start OS2COPY. │
│ >> This subdirectory MUST be included in the PATH statement in your │
│ >> Config.Sys system file +AND+ in your DOS PATH statement in │
│ >> in Autoexec.Bat. │
│ >> It is highly recommended to place this subdirectory entry │
│ >> immediately after "\OS2;" in both of these PATH statements │
│ │
│ Recommended installation procedure: │
│ │
│ Create a subdirectory named O immediately below the root of your │
│ From-Drive (eg. X:\O). │
│ │
│ Copy all files to this subdirectory. │
│ │
│ Include this subdirectory in the two PATH statements in Config.Sys │
│ and Autoexec.Bat, respectively. Reboot after editing these files. │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ Hands on: │
│ │
│ First take a look at what is in the following 7 bit ASCII files: │
│ YesNo.LNG, XCopy.Sw and InitEdit.LST │
│ │
│ >>> Make a full backup of your From drive and of anything you want to <<< │
│ >>> keep on your To drive. <<< │
│ │
│ >>> No other process may be active while this job is running <<< │
│ │
│ Stick to what the program and this documentation file tells you. │
│ │
│ Think while you work. │
│ │
│ Read - actually read - verify and respect the instruction displayed │
│ on your screen while running the two OS2COPY*.CMD-scripts. │
│ │
│ You +MUST+ edit the file 'YesNo.LNG' if copying a national language │
│ version other than English. Use any 7 bit ASCII text editor. │
│ │
│ You may need to edit InitEdit.LST - use any 7 bit ASCII text editor - │
│ but unless you have a very non-standard system or applications which │
│ keep hard coded drive information outside the OS*.INI files, I doubt it.│
│ │
│ Open a full screen command line session and type: │
│ │
│ OS2Copy <From Drive> with or without a trailing : │
│ │
│ you will later be prompted for <ToDrive> │
│ │
│ or just: │
│ │
│ OS2Copy │
│ │
│ in which case you will be prompted for <FromDrive> and later be │
│ prompted for <ToDrive> │
│ │
│ or, if you are absolutely positive, which drive letter will be │
│ assigned to the new TO system: │
│ │
│ OS2Copy <From Drive> <To Drive> │
│ │
│ Samples: │
│ │
│ OS2COPY D │
│ OS2COPY │
│ OS2COPY D: F │
│ OS2COPY D G │
│ │
│ Whichever you choose, you are twice asked to confirm the FROM and TO │
│ partition and file system. │
│ │
│ Although it is a simple task to make FDISK automatically delete and │
│ create the TO partition, for the sake of safety you are required to do │
│ this manually when FDISK has been started by the script. │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ Hands on 2.: │
│ │
│ React to the warnings and follow the instructions displayed on screen. │
│ │
│ WHEN you have made changes using FDISK - and this you MUST: │
│ You MUST delete any old partition that may exist where you want the new │
│ system to reside, create a new partition and add it to BootManager │
│ - or you will have to restart the procedure from scratch. │
│ │
│ Upon leaving FDISK you are requested to reboot using CTRL ALT DEL │
│ Do so. Do +NOT+ use the RESET button, FDISK has not finished yet. │
│ │
│ When your system reboots, the OS2Copy2 is automatically called from a │
│ temporary STARTUP.CMD file in your <From Drive> root directory. │
│ │
│ When copying is finished, you MAY have to copy your original STARTUP.CMD│
│ (now named STARTUP.@#@) back into STARTUP.CMD. │
│ I have never experienced this myself, but I know (inside info '-)) │
│ that the automatic restore of STARTUP.CMD may not always work. │
│ │
│ A backup of the original <From Drive> init files, Config.Sys and │
│ Autoexec.Bat are left in a subdirectory named <To Drive>\<From Drive> │
│ (eg. F:\D ). │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│>> The first time you boot from the newly created system, normally only <<│
│>> a skeleton WorkPlaceShell shows up <<│
│ │
│ ┌───────────────────────────────────────────────────────────────────┐ │
│ │ │ │
│ │ >>> !!! Reboot IMMEDIATELY using Control+Alt+Del !!! <<< │ │
│ │ │ │
│ │ !!! Do NOT perform an orderly shut down !!! │ │
│ │ !!! Do NOT make any changes to the WPS !!! │ │
│ │ │ │
│ └───────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ Copying an entire system including all configuration from one │
│ computer to the next one: │
│ │
│ Install and configure OS/2 on hard disk 2 (often D:) on From-computer. │
│ │
│ Physically install the hard disk to transfer to as disk 1 (C:) │
│ │
│ Begin installing OS/2 on hard disk 1 (C:) using the OS/2 installation │
│ diskettes. │
│ Configure the C: partition as PRIMARY (using FDISK). │
│ Insert the configured OS/2 system and the From-drive into BootManager. │
│ Abort when the C: disk has been formatted and boot manager is installed.│
│ │
│ Boot from D:. │
│ OS2Copy D: C: │
│ Remove hard disk 1 and insert it in To-computer. │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ Cracker section. │
│ │
│ The INITEDIT.EXE program includes a simple copy protection scheme. │
│ │
│ This may of course be broken like any other copy protection, │
│ but quite frankly, this would not be fair play, considering the many │
│ hours I have spent analyzing different system in order to make copying │
│ possible. No documentation was available, remember ? │
│ │
│ If you want to demonstrate your skills, write your own unlimited program │
│ - if you can - and place it in the Public Domain. │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ Legal section: │
│ │
│ The OS2COPY packet has been thoroughly tested and shown to work │
│ flawlessly on a number of different systems. │
│ │
│ It is, however, distributed * AS IS *. │
│ │
│ NO responsibility or any other obligation you can ever think of, │
│ shall be assumed, honored or anything else. │
│ │
│ >>> WARNING <<< │
│> You are strongly adviced +NOT+ to execute the INITEDIT program, <│
│> once it has told that no more copies are left. <│
│> The actions of the program are undefined. <│
│ │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ This Ståhle (C) software may NOT be used for production by a business, │
│ government agency or institution without payment of a license fee. │
│ │
│ A limited right to TEST this software is granted +anyone+ for │
│ * A TOTAL OF NO MORE THAN 10 COPIES * │
│ │
│ If you find the software of use to your company etc. and want to │
│ purchase it, you must order and pay for a number of copies inclusive of │
│ these 10 copies. │
│ │
│ Pricing: │
│ │
│ OS2COPY is ordered for a specific number of copies. │
│ 11 to 100 copies: US$ 5.00 for each copy. │
│ 101 to 500 copies: US$ 4.00 for each copy. │
│ 501 to 1000 copies: US$ 3.00 for each copy. │
│ No limit version: US$ 3,000.00 │
│ (A 'No limit' version which is "fully" automated │
│ ie. limiting manual work to little more than starting and rebooting │
│ the computer, may be ordered at no extra charge). │
│ │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ Public Domain 10 copy version. │
│ │
│ If and * ONLY IF * this packet is used on a private and │
│ personally owned computer, it is placed in the Public Domain. │
│ │
│ The Public Domain version will be able to perform 10 copies. │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ A word from the author: │
│ │
│ It may seem a kludge that names of files to be edited and subdirectory │
│ name converting tables etc. are placed in ASCII files instead of being │
│ hardcoded into program and scripts or being placed in some fancy │
│ binary files. │
│ It may also seem a kludge that so much of the code is written in REXX. │
│ │
│ This approach, however, enables you to │
│ (hopefully) keep pace with future updates of OS/2, without having to │
│ buy updates of this packet │
│ (not that I don't want to sell updates, but let's be reasonable). │
│ and to │
│ add init files related to programs, which create their own init files │
│ with "hard coded" partition information, instead of using OS2.INI │
│ and to │
│ add binary files, eg. programs, with "hard coded" drive letters │
│ and to │
│ add text files like Config.sys and ATM.INI including drive letters │
│ and to │
│ use this packet with the different national language versions of OS/2 │
│ and to │
│ use this packet even if you have changed the standard names of subdirs.│
│ │
│ Regards, John Ståhle │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ That's all. │
└───────────────────────────────────────────────────────────────────────────┘